Description Of Changes

This adds the remaining arguments in the install command's OptionSet and some more arguments in the global OptionSet as elements to the packages.config xml serialization schema.

Motivation and Context

This is useful for users wanting arguments that were previously not
available. It is also a pre-requisite for exporting remembered
arguments, as some of the remembered arguments were not available
in the previous available schema.

Some of the global arguments were not added:

• debug
• verbose
• trace
• nocolor
• noop
• allowunofficial
• proxy
• proxy-user
• proxy-password
• proxy-bypass-list
• proxy-bypass-on-local
• log-file

All of these appeared to either not be applicable to a single package (e.g. proxy related) or required earlier than the packages.config would get read (like log-file).

Testing

Save this as a packages.config file:

<?xml version="1.0" encoding="utf-8"?>
<packages>
   <package id="iperf2" prerelease="true" overrideArguments="true"
     notSilent="true" allowDowngrade="true" forceDependencies="true"
     skipAutomationScripts="true" user="string" password="string" cert="string"
     certPassword="string" ignoreChecksums="true" allowEmptyChecksums="true" 
     allowEmptyChecksumsSecure="true" requireChecksums="true" 
     downloadChecksum="string" downloadChecksum64="string" 
     downloadChecksumType="sha512" downloadChecksumType64="sha512"
     ignorePackageExitCodes="true" usePackageExitCodes="true"
     stopOnFirstFailure="true" exitWhenRebootDetected="true"
     ignoreDetectedReboot="true" disableRepositoryOptimizations="true"
     acceptLicense="true" confirm="true" limitOutput="true" cacheLocation="Z:\"
     failOnStderr="true" useSystemPowershell="true" noProgress="true"
   />
</packages>

Set the debugging arguments as install \path\to\packages.config

Then set a breakpoint at get_packages_from_config in ChocolateyPackageService, and step through the method, ensuring that the settings in the packageConfig get updated correctly.

Change Types Made

• Bug fix (non-breaking change)
• Feature / Enhancement (non-breaking change)
• Breaking change (fix or feature that could cause existing functionality to change)

Related Issue

Fixes #886
Depends on #2187

Change Checklist

• Requires a change to the documentation
• Documentation has been updated (Tracked in Document packages.config schema docs#403)
• Tests to cover my changes, have been added
• All new and existing tests passed.
• N/A PowerShell v2 compatibility checked